Mobile device activation for events

ABSTRACT

A method of activating mobile devices for events is provided. A mobile device owner pays for a subscription to receive local broadcasts of an event on a mobile device. An employee uses a scanner to scan a bar code on the mobile device, or the mobile device owner inputs information identifying the mobile device through a website. A database manager adds an identifier corresponding to the mobile device to an activation list. The broadcaster includes the activation list in the local broadcast stream, thereby activating the subscribed mobile devices for the event.

CROSS-REFERENCE TO RELATED APPLICATIONS

None.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

BACKGROUND

A mobile device user can use a mobile device to enhance the experienceof attending an event. For example, an automobile racing enthusiast canuse a particular mobile device at an automobile race track that enablesthe enthusiast to select portions of an automobile race to watch fromvarious broadcast cameras and to select different radio conversations tolisten between various automobile drivers and their pit crews.Broadcasters of events can rent such mobile devices to mobile deviceusers, but a rental process can require a significant amount of time andmoney to distribute the mobile devices to the users before the event andto collect the mobile devices after the event. Some enthusiasts whoregularly attend such events may prefer to purchase mobile devices forreuse at future events.

The above described situation presents unique problems that are notadequately addressed by existing device activation systems. For example,a large number of broadcast transmission receivers need to be activatedand/or deactivated on an event by event basis. Because the event isbroadcast only locally to mobile devices, the activation of the mobiledevice is continued when the mobile device is temporarily moved out ofthe limited broadcast range to avoid the need for reactivation when themobile device is returned to within the limited broadcast range.However, continuous activation creates problems for mobile devicesreported as lost or stolen, which need to be deactivated before orduring an event. Continuous activation also enables a mobile device toreceive broadcasts of subsequent events for which the mobile device isnot subscribed. The activation from different sources could beaccommodated, including internet subscriptions and point-of-saletransactions. Broadcasters and mobile device users each benefit from adevice activation system that addresses these and other problems.

SUMMARY

Accordingly, various systems and methods for event-based activation ofmobile devices are disclosed herein. In some method embodiments, amobile device is scanned for activation to receive a local broadcast ofan event. An identifier for the mobile device is added to an activationlist of identifiers. The activation list is provided to a broadcaster,wherein the broadcaster locally broadcasts the activation list toactivate mobile devices for the event.

A system embodiment includes an activation system, a database managerand an interface. The activation system identifies a mobile device foractivation to receive a local broadcast of an event. The databasemanager adds an identifier for the mobile device to an activation listof identifiers. The interface provides the activation list to abroadcaster, wherein the broadcaster locally broadcasts the activationlist to activate mobile devices for the event.

In yet another embodiment, a method of activating mobile devices forevents is provided. A user input identifying a mobile device foractivation to receive a local broadcast of an event is obtained. Anidentifier for the mobile device is added to an activation list ofidentifiers. The activation list is provided to a broadcaster, whereinthe broadcaster locally broadcasts the activation list to activatemobile devices for the event.

These and other features and advantages will be more clearly understoodfrom the following detailed description taken in conjunction with theaccompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and theadvantages thereof, reference is now made to the following briefdescription, taken in connection with the accompanying drawings anddetailed description, wherein like reference numerals represent likeparts.

FIG. 1 shows an illustrative mobile device activation system accordingto some embodiments of the present disclosure.

FIG. 2 shows a schema for a mobile device activation database accordingto some embodiments of the present disclosure.

FIG. 3 shows an illustrative mobile device activation method accordingto some embodiments of the present disclosure.

FIG. 4 shows a block diagram of an illustrative mobile device activationcomputer according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

It should be understood at the outset that although implementations ofvarious embodiments of the present disclosure are described below, thepresent system may be implemented using any number of techniques,whether currently known or in existence. The present disclosure shouldin no way be limited to the implementations, drawings, and techniquesdescribed below, but may be modified within the scope of the appendedclaims along with their full scope of equivalents.

Various methods and systems of mobile device activation are provided.After a mobile device owner pays for a subscription to receive localbroadcasts of an event on a mobile device, an employee can use a scannerto scan a bar code on the mobile device, or the mobile device owner caninput information identifying the mobile device through a website. Someembodiments activate mobile devices that are rented as well as mobiledevices that are sold. A database manager adds an identifiercorresponding to the mobile device to an activation list. Someembodiments check a deactivation list before adding the identifier tothe activation list to insure that the mobile device has not beenreported as lost or stolen. The broadcaster includes the activation listin the local broadcast stream, thereby activating the subscribed mobiledevices for the event. Some embodiments broadcast an event code tomaintain activation of subscribed mobile devices. In some embodiments,an activation problem is addressed by broadcasting a universalactivation code to activate all mobile devices at the event until theproblem is corrected, eliminating the possibility of activation problemsinterrupting the broadcast for subscribed mobile devices. In thismanner, the subscribed mobile devices are activated efficiently on anevent-by-event basis.

FIG. 1 shows an illustrative system 100 for implementing mobile deviceactivation methods according to some embodiments of the presentdisclosure. The system 100 is shown as including a desktop computer 102,although any electronic device having some amount of computing powercoupled to a user interface can be configured to carry out aspects ofthe methods disclosed herein. Among other things, servers, portablecomputers, personal digital assistants (PDAs) and mobile phones can beconfigured to carry out aspects of the disclosed mobile deviceactivation methods.

As shown, the desktop computer 102 comprises a chassis 104, a display106, and input devices 108 and 116. The chassis 104 comprises aprocessor, memory, and information storage devices. One or more of theinformation storage devices can store programs and data on removablestorage media such as a floppy disk 110 or an optical disc 112. Thechassis 104 can further comprise a network interface 114 that allows thedesktop computer 102 to receive information via a wired or wirelessnetwork, represented in FIG. 1 by a phone jack.

The chassis 104 is coupled to the display 106 and the input device 108to interact with a user of a mobile device activation system. Thedisplay 106 and the input device 108 can together operate as a userinterface. The input device 108 is shown as a keyboard, but can takemany alternative forms such as a keypad, a camera, a microphone, orother means for receiving information from a user, information such asidentifiers of mobile devices for activation to receive a localbroadcast of an event.

A scanner 116 can serve as an input device to the desktop computer 102,specifically by identifying a mobile device 118 for activation toreceive a local broadcast for an event. For example, the scanner 116identifies the mobile device 118 by scanning a barcode on the mobiledevice 118. The owner or user of the mobile device 118 can selectaspects of the local broadcast to receive on the mobile device 118.

The desktop computer 102 can communicate through the network interface114 and a wired or wireless network 120 with a database server 122,which in turn can communicate with various devices, such as a mobiledevice owner computer 124 and a broadcast server 126. Alternatively, ifthe scanner 116 has some of the capabilities of the desktop computer102, the scanner 116 can bypass the desktop computer 102 to communicatewith the database server 122 through the wired or wireless network 120.The desktop computer 102 or the scanner 116 can communicate identifiersof mobile devices for activation to the database server 122, which cancompile an activation list of mobile devices for activation. The ownerof the mobile device 118 can enter input to the mobile device ownercomputer 124 identifying the mobile device 118 for activation to receivea local broadcast of an event. The mobile device owner computer 124 cancommunicate the identifier for the mobile device 118 through the wiredor wireless network 120 to the database server 122. The broadcast server124 can retrieve the activation list of mobile devices for activationfrom the database server 122 through the wired or wireless network 120.Then the broadcast server 124 can be accessed by broadcastcommunications facilities to retrieve the activation list for inclusionin the broadcast stream through a broadcast network 128 to the mobiledevices 118, 130, and 132 by a standard wireless telephony protocol(such as code division multiple access), a wireless Internet connection,WiMAX, or some other means of wireless communication.

Turning now to FIG. 2, a schema 200 for a mobile device activationdatabase is depicted according to some embodiments of the presentdisclosure. A mobile device activation system can use a database managerapplication to manage such a database of device data, subscriptionsdata, transactions data, and event data to record subscriptions formobile devices to receive local broadcasts of events and to activatemobile devices to receive local broadcasts of events. The diagram 200shows a devices 202 table, a subscriptions 204 table, a transactions 206table, and an events 208 table. The numbers and types of tables and dataare depicted for the purpose of an illustrative example only, as thediagram 200 can include any number or types of tables and data.

The device 202 table can include data for each mobile device 118. Thedevices 202 table includes physical identifier 210 field, electronicidentifier 212 field, rental or retail 214 status, and stolen or missing216 status. The physical identifier 210 field can be an identifier thatuniquely identifies the mobile device 118 physically, such as a bar codeexternally located on the surface of the mobile device 118. Theelectronic identifier 212 can be a unique electronic identifier that isinternal to the mobile device 118, such as an electronic serial numberthat is burned into a memory location in the mobile device 118.

The retail or rental 214 status can specify whether the mobile device118 is a mobile device for a retail owner, such that the mobile device118 can be purchased or has been purchased, or a mobile device for arental user, such that the mobile device 118 can be rented on the basisof an event. If the mobile device 118 has been rented previously, themobile device 118 can be subsequently sold, such as a mobile device 118refurbished for sale. The stolen or missing 216 status can specifywhether a retail owner or rental user reported the mobile device 118 isstolen or missing.

The subscriptions 204 table includes data for subscriptions by mobiledevice owners to receive local broadcast of events on their mobiledevices. The subscriptions 204 table includes subscriber identifier 218field, device physical identifier 220 field, event identifier 222 field,subscription date 224 field, season subscription 226 field, andsubscription user identifier 228 field. The subscription identifier 218field can be a unique identifier for each recorded subscription by amobile device owner to receive local broadcasts of events on the mobiledevice 118. The device physical identifier 220 field can uniquelyidentify one mobile device by a physical identifier, such as a bar codelocated on the external surface of the mobile device 118. The devicephysical identifier 220 can associate each subscriptions 204 table withone devices 202 table for a particular mobile device. The eventidentifier 222 field can uniquely identify one particular events 208table for each subscriptions 204 table.

The subscription date 224 field can specify when an owner of the mobiledevice 118 subscribes to receive a local broadcast of an event on themobile device 118. The season subscription 226 field can specify whethera subscription is for an entire season of events, rather than asubscription for a single event. Additionally, the season subscription226 field can specify that a subscription is for a combination ofevents, such as a consecutive or non-consecutive series of events for ageographic region, rather than a single subscription or a seasonsubscription. The subscription user identifier 228 field can identifythe mobile device activation system user who recorded the subscription.

The transactions 206 table includes data for transactions regarding eachmobile device 118. The transactions 206 table includes transactionidentifier 230 field, type 232 field, description 234 field, deviceelectronic identifier 236 field, timestamp 238 field, and transactionuser identifier 240 field. The transaction identifier 230 field canuniquely identify a transaction regarding the mobile device 118, such asby use of a transaction number. The type 230 field can specify the typeof transaction, such as a sale of the mobile device 118 or a return ofthe mobile device 118 for repair. The description 234 field can specifyadditional information for a transaction beyond the type 232 field, suchas the identification of a rental mobile device loaned to a mobiledevice owner who returned a retail mobile device for repair. The deviceelectronic identifier 236 field can uniquely identify the mobile device118 for the transactions 206 table, such as by an electronic serialnumber that is burned into a memory location for the mobile device 118.The timestamp 238 field can specify the time and date for a transaction,while the transaction user identifier 240 field can identify the mobiledevice activation system user who recorded the transaction.

The events 208 table includes data for events broadcast locally to themobile device 118. The events 208 table includes identifier 242 field,name 244 field, start date and time 246 field, and end date and time 248field. The identifier 242 field is a unique identifier for an event,such as an event number, by which one particular subscriptions 204 tablecan be associated with one particular events 208 table. The names 244field can specify the name of an event, such as the name of a particularautomobile race known by its location. The start date and time 246 fieldcan specify the start date and time for the event, which is when thebroadcaster may begin locally broadcasting the event to mobile devices.The end date and time 248 field can specify the end date and time for anevent, which is when the broadcaster may stop locally broadcasting theevent to mobile devices.

Turning now to FIG. 3, an illustrative mobile device activation methodis depicted according to some embodiments of the present disclosure. Themobile device activation method enables a mobile device activationsystem to record subscriptions for mobile devices to receive localbroadcasts of events and to activate mobile devices to receive localbroadcasts of events.

In box 302, a mobile device activation system determines whether toreceive input through a user interface. If the mobile device activationsystem determines to receive input through the user interface, themethod continues to box 304. If the mobile device activation systemdetermines not to receive input through the user interface, the methodproceeds to box 306.

In box 304, the user interface obtains user input identifying the mobiledevice 118 for activation. For example, the mobile device owner entersthe physical identifier 210 field, such as a bar code identifier, forthe mobile device 118 through a website by using the mobile device ownercomputer 124. The website can require the mobile device owner to pay fora subscription to an event before permitting the mobile device owner toinput the physical identifier 210 field for the mobile device 118 to beactivated to receive the local broadcast of the event. Then the methodproceeds to box 310.

In box 306, the scanner 116 scans the mobile device 118 for activation.For example, a mobile device activation system employee uses the scanner116 to scan the bar code located on the exterior surface of the mobiledevice 118 to be activated. The mobile device activation system employeecan require the mobile device owner to pay for a subscription to anevent before scanning the mobile device 118 to be activated to receivethe local broadcast of the event.

In box 308, the scanner 116 displays data for the scanned mobile device118. For example, the scanner 116 displays the name 244 field to confirmthat the mobile device activation system employee is identifying themobile device 118 for activation to receive the local broadcast of theevent desired by the mobile device owner.

In box 310, a database manager application checks the physicalidentifier 210 field for the mobile device 118 against a deactivationlist of physical identifiers. For example, the database manager checksthe barcode for the mobile device 118 against a deactivation list ofphysical identifiers, a list compiled of physical identifiers for mobiledevices specified as stolen or missing by the stolen or missing 216status in the devices 202 table. The deactivation list of physicalidentifiers can include a bar code that matches a bar code scanned bythe mobile device activation system employee.

If the deactivation list specifies the mobile device 118 is lost orstolen, the mobile device activation system employee can notify themobile device owner that activation of the mobile device 118 is notpossible until the mobile device owner addresses the inclusion on thelist of the physical identifier 210 field for the mobile device 118.Alternatively, if the deactivation list specifies the mobile device 118is lost or stolen, the mobile device owner computer 124 can display amessage to notify the mobile device owner that activation of the mobiledevice 118 is not possible until the mobile device owner addresses theinclusion on the list of the physical identifier 210 field for themobile device 118.

In box 312, the database manager determines the electronic identifier212 field corresponding to the physical identifier 210 field for themobile device 118. If the electronic identifier 212 field for the mobiledevice 118 is the same as the physical identifier 210 field for themobile device 118, determining the electronic identifier 212 field cansimply require formatting the physical identifier 210 field in a formrecognized as the electronic identifier 212 field. However, to preventthe mobile device owner from activating the mobile device 118 for anevent without paying for the activation, the electronic identifier 212field for the mobile device 118 can differ from the physical identifier210 field for the mobile device 118, such that the mobile device ownerdoes not know the electronic identifier 212 field. For example, thedatabase manager references the scanned physical identifier 210 field inthe devices 202 table for the mobile device 118 to determine thecorresponding electronic identifier 212 field in the devices 202 tablefor the mobile device 118.

In box 314, the database manager adds the identifier for the mobiledevice 118 to an activation list of identifiers. For example, thedatabase manager adds the electronic identifier 212 field for the mobiledevice 118 to a list of electronic identifiers for mobile devicesalready subscribed to an event, those already approved for activation.The database manager can also record the subscription date 224, when amobile device owner subscribes to receive a local broadcast of an eventfor the mobile device 118. Additionally, the database manager can recordthe season subscription 226 field, whether a subscription is for anentire season of events, rather than a subscription for a single event.Furthermore, the database manager can record the subscription useridentifier 228 field, the mobile device activation system user whorecorded the subscription.

In box 316, an interface provides the activation list to a broadcaster,wherein the broadcaster locally broadcasts the activation list toactivate mobile devices for an event. For example, the broadcast server126 retrieves the activation list, which includes the electronicidentifier 212 field for each mobile device 118, 130, and 132 subscribedto the event, from the database server 122 through the wired or wirelessnetwork 120. Then the broadcast server 126 provides the activation listto the broadcast tower 128, which broadcasts the activation list to eachmobile device 118, 130, and 132. Each mobile device 118, 130, and 132 onthe activation list recognizes the broadcast of the correspondingelectronic identifier 212 field for the corresponding mobile device 118,130, and 132, and activates to receive the local broadcast of the event.If a mobile device 118 is not subscribed to the event, the activationlist broadcast by the broadcast tower 128 does not include theelectronic identifier 212 field for the mobile device 118, and themobile device 118 does not activate to receive the local broadcast ofthe event.

When the broadcast tower 128 broadcasts the activation list to eachmobile device 118, 130, and 132, the broadcast server 126 provides anevent code with the activation list to the broadcast tower 128. Thebroadcast of the event code begins based on the start date and time 246field for the corresponding event and stops based on the end date andtime 248 field for the corresponding event.

The broadcast tower 128 periodically broadcasts the event code and theactivation list for multiple reasons. First, a mobile device owner canphysically turn on their mobile device 118 at any time after broadcastof the activation list begins. Periodic broadcasting on the activationlist insures that the mobile device 118 is activated for each mobiledevice owner who has subscribed to the event, regardless of when themobile device owner turned on their mobile device 118.

Additionally, the broadcast tower 128 periodically broadcasts the eventcode as part of an additional check for stolen or lost mobile devices.The input continually received by the mobile device activation systemincludes not only identifications of mobile devices for activation, butalso identifications of mobile devices for deactivation. If a mobiledevice owner loses the mobile device 118 or has the mobile device 118stolen, the user can enter input to the mobile device activation systemthat modifies the deactivation list to specify the mobile device 118 islost or stolen. Similar to the situation when the mobile deviceactivation system activates the mobile device 118 that subscribed to theevent following the beginning of the event, even after the event beginsthe mobile device activation system can remove the identification of themobile device from the activation list to deactivate the mobile device118 that is reported as lost or stolen.

Furthermore, associating the event code with the activation list ensuresthat each mobile device 118, 130, and 132 is activated to receivesignals only at that event. Once activated by the broadcast of the eventcode for the current event and the activation list, including theelectronic identifier 212 field for the mobile device 118, the mobiledevice 118 maintains activation as long as the mobile device 118continues to receive broadcasts streams having the specified event codefor the event. Once the mobile device 118 is no longer receivingbroadcasts of the event code, because the event is over or because themobile device owner takes the mobile device 118 out of the localbroadcast range of the broadcast tower 128, the mobile device 118deactivates. Therefore, at a subsequent event, for which the mobiledevice 118 is not subscribed, the mobile device 118 will not beactivated because the mobile device 118 no longer receives the eventcode that maintained activation of the mobile device 118 for theprevious event. Additionally, the mobile device 118 will not activatebecause the activation list broadcast by the broadcast tower 128 nolonger includes the electronic identifier 212 field for the mobiledevice 118.

If the activation list is corrupted during an event, the broadcasterdoes not want the activation list corruption to result in the loss ofactivation for all subscribing mobile devices during the event.Therefore, in some embodiments, the broadcaster embeds the universalactivation code in the broadcast stream. When the broadcast tower 128broadcasts the universal activation code, each mobile device receivingthe broadcast is activated to receive local broadcasts of the event,regardless of whether the mobile device 118 is subscribed for the eventor not. Once the activation list is restored, the database managerprovides the restored activation list to the broadcast server 126, andthe broadcast tower 128 broadcasts the restored activation list insteadof the universal activation code. Then the mobile devices subscribed tothe event maintain activation, but any mobile devices not subscribed tothe event deactivate due to the absence of broadcasts of the universalactivation code. The universal activation code can include an activationlist of the electronic identifier 212 field for each mobile device 118,130, and 132 listed in the database. Alternatively, the universalapplication code can include a separate data code used only foractivating all mobile devices within the local broadcast range.

In addition to activating mobile devices sold to mobile device owners,the mobile device activation system can also activate mobile devicesrented to mobile device users. A rental mobile device 118 can be scannedfor activation, as in box 306, or a mobile device activation system usercan input an identifier for the rental mobile device 118 through a userinterface, as in box 304. Alternatively, all rental mobile devicesreturned for inventory (by inputting identifiers through a userinterface or scanning) following a previous event can be added to theactivation list for a subsequent event. Because the activation list foran event does not include the electronic identifier 212 field for arental mobile device not returned prior to the event, stolen or missingrental devices do not activate for subsequent events.

The database manager can use the data in the transactions 206 table tohandle rental mobile devices that have been refurbished and sold asretail mobile devices. For example, the type 230 field specifies thetype of a transaction as a sale of the mobile device 118 that previouslyreceived broadcasts as a rental mobile device 118. The description 234field can specify additional information for the transaction beyond thetype 232 field, such as the name of the individual that purchased themobile device 118, the timestamp 238 field can specify the time and datefor the sale, and the transaction user identifier 240 field can identifythe mobile device activation system user who recorded the sale.

FIG. 4 shows a simplified functional block diagram 400 of the desktopcomputer 102 system according to some embodiments of the presentdisclosure. The chassis 104 may comprise a display interface 402, aperipheral interface 404, a processor 406, a modem or other suitablenetwork interface 408, a memory 410, an information storage device 412,and a bus 414. The desktop computer 102 may be a bus-based computer,with the bus 414 interconnecting the other elements and carryingcommunications between them. The display interface 402 may take the formof a video card or other suitable display interface that acceptsinformation from the bus 414 and transforms it into a form suitable forthe display 106. Conversely, the peripheral interface 404 may acceptsignals from the keyboard 108 and other input devices such as a pointingdevice 416, and transform them into a form suitable for communication onthe bus 414.

The processor 406 gathers information from other system elements,including input data from the peripheral interface 404, and programinstructions and other data from the memory 410, the information storagedevice 412, or from a remote location via the network interface 408. Theprocessor 406 carries out the program instructions and processes thedata accordingly. The program instructions may further configure theprocessor 406 to send data to other system elements, comprisinginformation for the user which may be communicated via the displayinterface 402 and the display 106, information such as data about themobile device 118 for activation to receive a local broadcast of anevent.

The network interface 408 enables the processor 406 to communicate withremote systems via a network. The memory 410 may serve as a low-latencytemporary store of information for the processor 406, and theinformation storage device 412 may serve as a long term (but higherlatency) store of information, including information such as anactivation list of identifiers for mobile devices for activation toreceive a local broadcast of an event.

The processor 406, and hence the desktop computer 102 as a whole,operates in accordance with one or more programs stored on theinformation storage device 412. The processor 406 may copy portions ofthe programs into the memory 410 for faster access, and may switchbetween programs or carry out additional programs in response to useractuation of the input device. The additional programs may be retrievedfrom the information storage device 412 or may be retrieved from remotelocations via the network interface 408. One or more of these programsconfigures the desktop computer 102 system to carry out at least one ofthe mobile device activation methods disclosed herein.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods may beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein, but may be modified withinthe scope of the appended claims along with their full scope ofequivalents. For example, the various elements or components may becombined or integrated in another system or certain features may beomitted, or not implemented.

What is claimed is:
 1. A mobile device activation method, comprising:scanning a mobile device for an identifier of the mobile device foractivation of the mobile device to receive a local broadcast of anevent; adding the identifier for the mobile device to an activation listcomprising a plurality of identifiers for mobile devices subscribed forthe event; providing the activation list to a broadcaster, wherein thebroadcaster locally broadcasts the event and the activation list withthe event to local mobile devices such that each of the local mobiledevices receives the activation list comprising the plurality ofidentifiers and each of the local mobile devices that detects theiridentifier on the activation list activates for the event; checking aphysical identifier for the mobile device against a deactivation list ofphysical identifiers; removing the identifier for the mobile device fromthe activation list for the event when a match of the identifier isfound in the deactivation list; and providing the activation listwithout the identifier to the broadcaster, wherein the broadcasterlocally broadcasts the activation list without the identifier to localmobile devices to deactivate the mobile device having the identifierthat was removed from the activation list for the event.
 2. The methodof claim 1 wherein adding the identifier for the mobile device to theactivation list of identifiers comprises determining an electronicidentifier corresponding to a physical identifier for the mobile device.3. The method of claim 1 wherein broadcasts of the activation listcomprise an event code for maintaining activation of the mobile devices.4. The method of claim 3 wherein the event code uniquely associates theactivation list with the event.
 5. The method of claim 1 furthercomprising providing a universal activation code to the broadcaster,wherein the broadcaster broadcasts the universal activation code toactivate all local mobile devices.
 6. The method of claim 1 wherein thebroadcaster locally broadcasts the activation list more than once duringthe event.
 7. The method of claim 1 wherein each of the mobile deviceshaving their identifier on the activation list for receiving the eventrecognizes the broadcast of their corresponding identifier and activatesto receive the local broadcast of the event.
 8. A mobile deviceactivation system, comprising: an activation system to receive anidentifier of a mobile device for activation of the mobile device toreceive a local broadcast of an event; a database manager to add theidentifier for the mobile device to an activation list comprising aplurality of identifiers for mobile devices subscribed for the event,and an interface to provide the activation list to a broadcaster,wherein the broadcaster locally broadcasts the activation list in abroadcast stream of the event to local mobile devices such that each ofthe local mobile devices receives the activation list comprising theplurality of identifiers and each of the local mobile devices thatdetects their identifier on the activation list activates for the eventand each of the local mobile devices that was previously activated forthe event that does not detect their identifier on the activation listfor the event deactivates for the event.
 9. The system of claim 8wherein the activation system comprises a scanner to receive theidentifier of the mobile device for activation.
 10. The system of claim9 wherein the scanner is further operable to display data for theidentified mobile device.
 11. The system of claim 8 wherein theactivation system comprises a user interface to receive the identifierof the mobile device for activation.
 12. The system of claim 8 whereinthe database manager is further operable to check a physical identifierfor the mobile device against a deactivation list of physicalidentifiers.
 13. The system of claim 8 wherein the database manager isfurther operable to determine an electronic identifier corresponding toa physical identifier for the mobile device.
 14. The system of claim 8wherein broadcasts of the activation list comprise an event code formaintaining activation of the mobile devices.
 15. The system of claim 8wherein the interface further provides a universal activation code tothe broadcaster, wherein the broadcaster broadcasts the universalactivation code to activate all local mobile devices.
 16. A mobiledevice activation method, comprising: obtaining a user input identifyinga mobile device for activation to receive a local broadcast of an event;adding an identifier for the mobile device corresponding to the userinput to an activation list comprising a plurality of identifiers formobile devices subscribed for the event; providing the activation listto a broadcaster, wherein the broadcaster locally broadcasts theactivation list to local mobile devices such that each of the localmobile devices receives the activation list comprising the plurality ofidentifiers and each of the local mobile devices that detects theiridentifier in the activation list activates for the event; and providinga universal activation code to the broadcaster if there is a problemwith the activation list, wherein the broadcaster locally broadcasts theuniversal activation code such that each of the local mobile devicesthat receives the universal activation code activates for the event. 17.The method of claim 16 wherein adding the identifier for the mobiledevice to the activation list of identifiers comprises checking the userinput identifying the mobile device against a deactivation list ofphysical identifiers.
 18. The method of claim 16 wherein adding theidentifier for the mobile device to the activation list of identifierscomprises determining an electronic identifier corresponding to the userinput identifying the mobile device.
 19. The method of claim 16 whereinbroadcasts of the activation list comprise an event code for maintainingactivation of the mobile devices.